Digital verified identification system and method

ABSTRACT

A digital verified identification system and method are presented for verifying and/or authenticating the identification of an entity associated with an electronic file, such as, for example the digital signatory thereof. In particular, the system and method include a module generating assembly structured to receive at least one verification data element, and at least one digital identification module structured to be associated with at least one entity. The digital identification module is capable of being disposed or embedded within at least one electronic file. Further, the digital identification module includes at least one primary component structured to at least partially associate the digital identification module with the entity, and one or more metadata components.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present specification is generally directed to a digital verifiedidentification system and method having at least one digitalidentification module structured to be embedded or otherwise disposedwithin one or more electronic files.

2. Description of the Related Art

In general, contracts, letters, messages, notes, and/or other hardcopies of papers or documents may be physically signed, for example,with a pen or other writing utensil, by one or more entities to identifythe provenance of the document and/or otherwise associate the documentwith the respective entity. In addition, often times a notary public orother witness is used or required assist in the verification orauthentication of the identity of the signatory of the document. Withthe advent of computers and the proliferation of the World Wide Web,however, many people and/or entities tend to conduct business orotherwise communicate electronically. As a result, various methods ofassociating an electronic file or document with one or more entities, orotherwise including electronic signatures on the electronic file ordocument, have been developed. For example, at least one common methodof electronically signing a document includes placing a forward orbackward slash prior to and/or following the signatory's typed name.Accordingly, an individual named John Doe might electronically sign adocument by placing “/John Doe/” on a signature line that is typicallyat or near the end of the document. These various electronic signaturesor identifiers, however, are rather difficult to authenticate, and assuch, it has become an arduous, if not impossible task to verify and/orauthenticate the identity of the signatory to a respectable degree.

Accordingly, there is a current need in the art for a digital verifiedidentification system structured to facilitate authenticating and/orverifying the identity of an electronic signatory to a file and/orotherwise structured to associate an electronic file with one or moreentities. As such, it would be beneficial to provide a system having oneor more digital identification modules structured to be embedded orotherwise disposed within at least one electronic file or document. Inparticular, it would be advantageous if the digital identificationmodule is created or otherwise generated by a module generating assemblyutilizing at least one verification data element corresponding to theone or more entities, such as, for example, a signatory of theelectronic file.

It addition, it would be particularly beneficial to provide a digitalverified identification system wherein the one or more digitalidentification modules include at least one primary component and atleast one metadata component having, for example, various identifyinginformation and/or reference codes and/or numbers. In particular, theprimary component may include the signature or other identifying indiciaof the respective signatory. Additionally, the metadata component(s) mayinclude, for example, a module or entity reference code and/or number,the signatory's name, the date/time, or other data corresponding to thesignatory and/or the signatory's digital identification module.

SUMMARY OF THE INVENTION

The present specification is directed to a digital verifiedidentification system and method including a module generating assemblystructured to create at least one digital identification module, whereinthe digital identification module is structured to be embedded orotherwise disposed within one or more electronic files. Moreover, anentity, such as a signatory of an electronic document, may communicateat least one verification data element to the module generating assemblyprior to creating the digital identification module. The verificationdata element(s) may include any indicia or data structured to facilitatethe verification or identification of the corresponding entity. Forexample, the verification data element(s) may include a username and/orpassword, date of birth, social security number, driver's licensenumber, credit card number, etc.

Additionally, in at least one embodiment, the digital identificationmodule includes a file or object that may be imported into a computerapplication to facilitate embedding or otherwise disposing the digitalidentification module into an electronic file, such as, for example aword processing document. In at least one embodiment, however, themodule generating assembly is at least partially integrated within thecomputer application, e.g., an interactive word processing program, suchthat the digital identification module created therefrom may be directlyembedded within the electronic file rather than first being importedinto the computer application.

Furthermore, the digital identification module of at least oneembodiment includes at least one primary component and at least onemetadata component. The primary component may include, for example, adigital representation of a signature and/or one or more referencecodes, numbers, or characters, the significance of which will beapparent from the discussion below. The primary component is generallyvisible or perceptible to a reader, recipient, or other user of theelectronic document. In addition, the metadata components may berepresentative of the one or more of the verification data elements, orother data corresponding to the digital identification module and/orentity, including the date and time, location of the entity, etc.

A reader, recipient, or other user of the electronic document may accesssome or all of the metadata components of the digital identificationmodule, for example, by activating the module. Specifically, the usermay hover a mouse or other pointing device thereon, or click on thedigital identification module via the mouse or pointing device. Inaddition, a user may communicate the one or more reference codes, whichmay be part of the primary component(s) and/or the metadatacomponent(s), to a third party to access some or all of the metadatacomponents.

These and other objects, features and advantages of the presentinvention will become more clear when the drawings as well as thedetailed description are taken into consideration.

BRIEF DESCRIPTION OF THE DRAWINGS

For a fuller understanding of the nature of the present invention,reference should be had to the following detailed description taken inconnection with the accompanying drawings in which:

FIG. 1 is a schematic representation of one embodiment of the digitalverified identification system of the present specification.

FIG. 1A is a schematic representation of another embodiment of thedigital verified identification system of the present specification.

FIGS. 2, 2A, and 2B are illustrative of one embodiment of the modulegenerating assembly of the digital verified identification system of thepresent specification.

FIG. 3 is a schematic representation of one embodiment of the computerapplication of the digital verified identification system of the presentspecification.

FIG. 3A is a schematic representation of another embodiment of thecomputer application of the digital verified identification system ofthe present specification.

FIG. 4 is a schematic representation of yet another embodiment of thedigital verified identification system of the present specification.

FIG. 5 is a schematic representation of another embodiment of thedigital verified identification system of the present specification.

FIG. 6 is a schematic representation of one embodiment of the digitalidentification module of the present specification.

FIG. 7 is a flow chart of one embodiment of the method of digitalidentification verification of the present specification.

Like reference numerals refer to like parts throughout the several viewsof the drawings.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

As shown in the accompanying drawings, and in particular FIGS. 1 and 1A,the present specification relates to a digital verified identificationsystem, generally indicated as 10. At least one embodiment of thepresent system 10 includes one or more digital identification modules 20structured to be associated with one or more entities 30 such as, forexample, an individual, a group of individuals, and/or a signatory of adocument or file. In particular, as will become apparent from thediscussion below, the digital identification module(s) 20 of the variousembodiments of the present system 10 may include virtually any file,item, object, or device structured to be embedded or otherwise disposedwithin an electronic file or document 40. In at least one embodiment ofthe present system 10, the digital identification module 20 includes animage or photographic file, including, but in no way limited to a JointPhotographic Experts Group (“JPEG”) file, bitmap or pixmap file,Portable Network Graphics (“PNG”) file, Graphics Interchange Format(“GIF”) file, and/or any other file(s) or documents. Additionally,however, in at least one other embodiment of the system 10, the digitalidentification module 20 includes one or more objects, codes and/orother devices structured to facilitate the practice of the presentsystem 10 in the intended fashion.

Furthermore, at least one embodiment of the system 10 of the presentspecification includes a module generating assembly 50 structured toreceive at least one verification data element 52 corresponding to theat least one entity 30. In addition, the module generating assembly 50is further structured to create or otherwise generate the digitalidentification module 20 of the various embodiments of the presentsystem 10. More in particular, FIGS. 2, 2A, 2B represent at least oneillustrative embodiment of the module generating assembly 50 of thepresent system 10. The verification data element(s) 52 of the variousembodiments of the present system 10 include any information or datastructured to at least partially facilitate authenticating and/orverifying the identity of the respective individual, person, or otherentity 30. Particularly, as illustrated in FIG. 2, the module generatingassembly 50 may include or require, for example, the entity 30 to enter,type in, or otherwise communicate a username and/or a password in orderto gain access to or otherwise use the module generating assembly 50.The username and/or password may be utilized as the verification dataelement(s) 52 for purposes of verification and/or authentication of therespective entity 30.

Additionally, in at least one embodiment of the module generatingassembly 50, as illustrated in FIG. 2A, a user or entity 30 may create anew account, for example, by communicating one or more verification dataelements 52 to the module generating assembly 50. For illustrativepurposes only, the verification data elements 52 as shown in FIG. 2Ainclude the entity's name, address, date of birth (“DOB”), socialsecurity number (“SSN”), Driver's License number (“DL No.”), a creditcard number (“CC No.”), etc. In addition, as represented by referencenumeral 52′ in FIG. 2A, the entity 30 may upload, import, or otherwiseindicate a file, such as an image or picture file, representing adigital rendition of the entity's signature, for example.

As mentioned above, the module generating assembly 50 of the variousembodiments of the system 10 is structured to create at least onedigital identification module 20. In particular, assuming an entity 30has already logged into the module generating assembly 50 or otherwisecommunicated at least one verification data element 52 thereto, in atleast one embodiment of the present system 10, the particular electronicfile 40 in which the module 20 will be embedded or disposed, may bespecified or pre-selected, as shown at reference numeral 40′ in FIG. 2B,prior to creating the digital identification module 20. In such anembodiment, the digital identification module 20 may be structured to beembedded, disposed, or otherwise operable only with the pre-selectedelectronic file 40. In yet another embodiment, however, as representedby reference numeral 40″ in FIG. 2B, the number of electronic documentsin which the digital identification module 20 can be embedded ordisposed into, or otherwise operate with may be pre-selected orpre-specified. In such an embodiment, when the digital identificationmodule 20 has been embedded or disposed into electronic documentstotaling the pre-selected number, the digital identification module 20may be automatically deleted, become inoperable, or otherwise bedisposed in an inactive state. It is also contemplated that, in at leastone embodiment, each digital identification module 20 is structured tobe embedded within a single electronic document 40.

Additionally, in at least one embodiment of the present system 10, thedigital identification module 20 is structured to be disposed in aninactive state upon manipulating the content(s) 42 of the electronicfile 40 subsequent to embedding the digital identification module 20therein. In particular, if the content(s) 42 of the electronic file 40are manipulated, deleted, changed, or added to subsequent to embeddingor otherwise disposing the digital identification module 20 therein, thedigital identification module 20 may be automatically deleted or removedfrom the electronic file 40. In addition, the digital identificationmodule 20 may be crossed out, or automatically stamped “void”, forexample.

Moreover, in at least one embodiment of the present system 10, once thedigital identification module 20 is embedded or otherwise disposedwithin the electronic file 40, a user or recipient of the file 40 cannotdelete or remove the digital identification module 20 therefrom. Inaddition, should an electronic copy of the electronic file 40 be madesubsequent to embedding or otherwise disposing a digital identificationmodule 20 therein, the copy of the electronic file 40 may also include acopy of the digital identification module 20 embedded therein.

Furthermore, as illustrated in FIGS. 3 and 3A, at least one embodimentof the present system 10 includes a computer application 60 structuredto embed or otherwise dispose the digital identification module 20within the electronic file 40. The computer application 60 may include,but is not limited to, any program structured to create or otherwisemanipulate an electronic file 40. In particular, the computerapplication 60 may include virtually any interactive file handlingprogram and/or word processing program, such as, MICROSOFT® WORD,MICROSOFT® WORD PERFECT, and/or ADOBE® ACROBAT®. For illustrativepurposes only, as shown by the pull-down menu item 62 in FIG. 3, thecomputer application 60 may be structured to import or insert thedigital identification module 20 from a file or an external program,such as the module generating assembly 50. In such an embodiment, themodule generating assembly 50 may be a program which is completelyindependent of the interactive word processing program or other computerapplication 60. For example, the module generating assembly 50 of atleast one embodiment is a separate and independent program or servicethat may be structured to create an object or file, such as a JPEG, GIF,PNG, or a signature file, which can be imported, inserted, or otherwiseembedded or disposed within the electronic file 40 by virtue of thecomputer application 60. Accordingly, the module generating assembly 50of at least one embodiment of the present system 10 includes a separateprogram that is run or executed on the entity's 30 computer or otherdevice. When the entity 30 desires to create a digital identificationmodule 20, the entity 30 may access the module generating assembly 50,either via the computer application 60, or independent of the computerapplication 60.

In yet another embodiment, however, as shown in FIG. 3A, the modulegenerating assembly 50 may be at least partially integrated within theinteractive word processing program, or other computer application 60.As such, the computer application 60 may include a feature, option, orfunction, represented by pull-down menu item 64, that is structured toinitiate the module generating assembly 50 so as to create and/or embedthe digital identification module 20 within the electronic file 40.

In addition, and as illustrated in FIG. 4, the module generatingassembly 50 of the present system 10 may be accessed via at least oneinteractive computer network 70, such as the World Wide Web via theInternet. In such an embodiment, the module generating assembly 50 maybe accessed through a web site whereby the digital identification module20 may be downloaded and then embedded or otherwise disposed within theelectronic file 40.

It is also contemplated that the electronic file 40 may include adocument, form, or other file disposed on the World Wide Web. In such anembodiment, the digital identification module 20 may be uploaded to theparticular web server, web site, or other form or document on the WorldWide Web so as to associate the particular file with the respectiveentity 30. Of course if the digital identification module 20 is createdvia a web site, the module 20 may not need to be uploaded in certaincircumstances.

It should be apparent that the module generating assembly 50 of thevarious embodiments of the present system 10 may include one or moredevices or mechanisms structured to facilitate the practice of thepresent system 10 in the intended manner. For example, as illustrated inFIG. 5, at least one embodiment of the module generating assembly 50 mayinclude a local assembly 54 or other program, application, or plug-indisposed on the entity's 30 computer or included within the computerapplication 60, such as the interactive word processing program, asdescribed above. In addition, the module generating assembly 50 may alsoinclude a remote assembly 56 or program accessible via an interactivecomputer network 70, such as the World Wide Web, and disposable in acommunicative relation with the local assembly 54. In at least oneembodiment, the remote assembly 56 is structured to store or otherwiseinclude various information or data about the entity 30, such as, forexample the entity's account, verification data element(s), etc. Thatinformation may then be communicated to the local assembly 54 via theinteractive computer network 70. Accordingly, the local assembly 54 ofat least one embodiment, may be structured to thereafter create thedigital identification module 20. In yet another embodiment, however,the remote assembly 56 is structured to create the digitalidentification module 20, which is then communicated to the localassembly 54.

Furthermore, as illustrated in FIG. 6, the digital identification module20 of at least one embodiment of the present system 10 includes aprimary component 22 and one or more corresponding metadata components24. In particular, the primary component 22 of the digitalidentification module 20 is preferably at least partially visible orperceptible to a user reviewing the electronic file 40. Furthermore,should the electronic file 40 be printed, in at least one embodiment,the primary component 22 is structured to be at least partially visibleon the physical or printed document. Accordingly, in at least oneembodiment of the present system 10, the primary component 22 mayinclude a digital signature of the entity 30 or signatory of thedocument, or other element structured to at least partially associatethe electronic file 40 with the entity 30. In addition, the primarycomponent 22 may comprise a graphical representation of the digitalsignature, and as such, may include, for example, a JPEG, BMP, PNG, orGIF file.

Moreover, as above, at least one embodiment of the present system 10further includes one or more corresponding metadata components 24. Inparticular, the corresponding metadata components 24 are structured tocorrespond to, for example, the entity 30, the respective digitalidentification module 20, the entity's computer, the one or moreverification data elements 52, etc. Accordingly, in at least oneembodiment, the metadata component(s) 24 include, but are in no waylimited to the date and time the digital identification module 20 wascreated, the computer or device the digital identification module 20 orelectronic file 40 was created on, the computer or device that embeddedthe digital identification module 20 into the electronic file 40, GPSlocation of the entity 30 or computer/device that created or embeddedthe file 40, the country, zip code, state, city or other informationpertaining to the location of the entity 30, the location of thecomputer or device that embedded the digital identification module 20into the electronic file 40, tracing information to the computer thatcreated or embedded the module 20, notes, etc. In particular, themetadata component(s) 24 may include a graphical representation of adigital signature, and as such, may include, for example, a JPEG, BMP,PNG, or GIF file. Additionally, the metadata component(s) 24 may includecomputer identification numbers or characters corresponding to thecomputer in which the digital identification module 20 was created,initiated, or otherwise institutes, such as the entity's 30 computer. Assuch, the metadata component(s) 24 may include, for example, acomputer's Media Access Control (“MAC”) address or other identificationnumbers, characters, or data.

Furthermore, in at least one embodiment, the metadata component(s) 24may include a unique module reference code or number corresponding tothe digital identification module 20, or a unique entity reference codeor number corresponding to the entity 30. Accordingly, once anindividual, such as the recipient of the electronic file 40, hasknowledge of or access to the module or entity reference codes, it iscontemplated that the reference codes may be communicated to the modulegenerating assembly 50, or other third party, such as, for example a website, and gather more information about the entity 30 or the particulardigital identification module 20. For example, the third party may haveinformation to verify the entity 30 or signatory, or otherwise providesome or all of the metadata components 24 either corresponding to theentity 30, the respective digital identification module 20, or both.

In addition, the digital identification module 20 of at least oneembodiment may be structured to display, show, or reveal some or all ofthe corresponding metadata components 24, such as, for example, upon theoccurrence of one or more predetermined events, including, but notlimited to, a mouse over or clicking event. Accordingly, as illustratedin FIG. 6, in at least one embodiment, when a mouse, pointer, or otherlike device 12 is disposed, hovered, or rolled over the digitalidentification module 20, such as, for example, the primary component 22thereof, the digital identification module 20 is structured to revealsome or all of the metadata component(s) 24 in a pop-up box 14, or otherlike structure or device. It is also contemplated that in at least oneembodiment of the present system 10, a user must click on the digitalidentification module 20, or primary component 22 thereof, in order toview some or all of the metadata component(s) 24. Additionally, in yetanother embodiment, when a user disposes or hovers the mouse or otherpointing device 12 over the digital identification module 20, somemetadata components 24 are revealed, and when a user clicks on themodule 20 or primary component 22, additional and/or other metadatacomponents 24 are revealed. Furthermore, in yet another embodiment, auser may need to communicate a valid username and password or otheridentification information prior to viewing some or all of the metadatacomponents 24 of the particular digital identification module 20.

Moreover, the identification of the entity 30 with which the electronicfile 40 is associated may be verified by the module generating assembly50. For example, as above, the verification data element(s) 52 mayinclude, for example, identification information such as a name,address, and credit card number. Accordingly, the module generatingassembly 50 may, in at least one embodiment, contact the correspondingfinancial institution for verifying that the verification dataelement(s) 52 indeed corresponds to the entity 30 prior to generatingthe digital identification module 20. On the other hand, at least oneembodiment of the present system 10 is structured to provide metadatacomponents 24 to the user or recipient of the electronic file 40 suchthat the user or recipient can verify the identity of the respectiveentity 30 associated with the electronic file 40.

In addition, and as illustrated in FIG. 7, the present specificationrelates to a method of digital identification verification, generallyindicated as 100. In particular, as illustrated at 102 in FIG. 7, atleast one embodiment of the method 100 includes receiving at least oneverification data element from an entity. As above, the verificationdata element may include a username and/or password, the entity's name,address, date of birth, social security number, driver's license number,credit card number, etc. In the various embodiments of the presentmethod 100, as described in greater detail above, the entitycommunicates the at least one verification data element to a modulegenerating assembly, which may be accessed via an interactive computernetwork. In addition, the module generating assembly may be at leastpartially integrated within a computer application such as aninteractive word processing program, as a feature, option, or plug-infor example. It is also contemplated that the module generating assemblyis completely separate and independent from the interactive wordprocessing program or other like computer application structured tomanipulate electronic files.

Furthermore, still referring to FIG. 7, the method 100 of the presentspecification includes creating at least one digital identificationmodule, as illustrated at 104. More in particular, in at least oneembodiment, the entity may log into an account, or otherwise create anew account with the module generating assembly 50. Either in theprocess of creating a new account, logging in, or while logged in, theentity communicates at least one verification data element thereto.Furthermore, in at least one embodiment, the module generating assemblyis structured to at least partially create the digital identificationmodule(s), for example, by combining at least one primary component withat least one metadata component. The primary component may berepresentative of a digital rendition of the entity's signature, or areference code. The metadata component(s) may include othercorresponding data, including but not limited to the verification dataelements, the date and time of creating the identification module, thelocation or other identifying information corresponding to the computeror device that was used to embed the identification module, etc.

Moreover, the various embodiments of the method 100 of the presentspecification include embedding the at least one digital identificationmodule within the electronic file, represented as 106 in FIG. 7.Accordingly, in at least one embodiment, the entity may import a file,i.e., a digital identification module, created by the module generatingassembly into the electronic file via a computer application, such as,for example, an interactive word processing program or other applicationstructured to create or manipulate electronic files, or otherwisestructured to facilitate the practice of the present method in theintended fashion. As above, however, in at least another embodiment, themodule generating assembly is at least partially integrated within thecomputer application, such as the word processing program, for example,as a feature, option, or plug-in. In such an embodiment, the digitalidentification module need not be imported, but is rather created, atleast in part, by the module generating assembly.

Once the digital identification module is embedded within the electronicfile, at least one embodiment of the present method 100 includesrevealing at least one metadata component, represented as 108 in FIG. 7.More in particular, a user, such as the recipient of the electronicfile, may activate the digital identification module by hovering a mouseor other pointing device over it, or by clicking on it with the mouse orother pointing device. In such an instance, at least one embodiment ofthe present method 100 will reveal some or all of the metadatacomponents, for example, via a pop-up box or other like structure ordevice. In addition, a user, such as the recipient of the electronicdocument may communicate a reference code to a third party, for example,the module generating assembly, a web site, or other device, object, orservice, and receive in return one or more metadata componentscorresponding to the respective digital identification module and/orentity. The reference code may be obtained via the metadata from thedigital identification module, however, in at least one embodiment, thereference code appears as part of the primary component thereof. Uponreceipt of the metadata components or other identifying information, theuser or recipient of the electronic file may verify the data to at leastpartially verify or authenticate the identification of the entityassociated with the digital identification module and/or electronicdocument.

Since many modifications, variations and changes in detail can be madeto the described preferred embodiment of the invention, it is intendedthat all matters in the foregoing description and shown in theaccompanying drawings be interpreted as illustrative and not in alimiting sense. Thus, the scope of the invention should be determined bythe appended claims and their legal equivalents.

Now that the invention has been described,

What is claimed is:
 1. A digital verified identification system,comprising at least one digital identification module structured to beassociated with at least one entity, a module generating assemblystructured to receive at least one verification data elementcorresponding to the at least one entity and create said at least onedigital identification module, said at least one digital identificationmodule being disposable within at least one electronic file, and said atleast one digital identification module comprising at least one primarycomponent structured to at least partially associate said digitalidentification module with said at least one entity, wherein said atleast one digital identification module is cooperatively structured tobe embedded within only a single electronic file.
 2. The digitalverified identification system recited in claim 1 further comprising atleast one computer application structured to embed said at least onedigital identification module within the electronic file.
 3. The digitalverified identification system recited in claim 2 wherein said at leastone computer application includes an interactive file handling program.4. The digital verified identification system recited in claim 1 whereinsaid module generating assembly is accessible via at least oneinteractive computer network.
 5. The digital verified identificationsystem recited in claim 1 wherein said at least one primary componentincludes a digital signature.
 6. The digital verified identificationsystem recited in claim 5 wherein said at least one primary componentincludes a graphical representation of said digital signature.
 7. Thedigital verified identification system recited in claim 1 wherein saidat least one digital identification module further comprises at leastone corresponding metadata component.
 8. The digital verifiedidentification system recited in claim 1 wherein said digitalidentification module further comprises a plurality of correspondingmetadata components.
 9. The digital verified identification systemrecited in claim 8 wherein said plurality of corresponding metadatacomponents are structured to be revealed in response to the occurrenceof at least one predetermined event.
 10. The digital verifiedidentification system recited in claim 9 wherein said at least onepredetermined event includes disposing a pointing device over saidprimary component.
 11. The digital verified identification systemrecited in claim 9 wherein said at least one predetermined eventincludes clicking on said primary component with a pointing device. 12.The digital verified identification system recited in claim 8 wherein atleast one of said plurality of corresponding metadata componentsincludes a module reference number corresponding to said at least onedigital identification module.
 13. The digital verified identificationsystem recited in claim 8 wherein at least one of said plurality ofcorresponding metadata components includes an entity reference numbercorresponding to the at least one entity.
 14. The digital verifiedidentification system recited in claim 8 wherein at least one of saidplurality of corresponding metadata components includes a graphicalrepresentation of a digital signature.
 15. The digital verifiedidentification system recited in claim 8 wherein at least one of saidplurality of corresponding metadata components includes a MAC addresscorresponding to a computer that instituted the creation of said digitalidentification module.
 16. The digital verified identification systemrecited in claim 1 wherein said at least one digital identificationmodule is cooperatively structured to correspond to a pre-selectedelectronic file.
 17. The digital verified identification system recitedin claim 1 wherein said at least one digital identification module isstructured to be disposed in an inactive state upon manipulating the atleast one electronic file subsequent to embedding said at least onedigital identification module therein.
 18. The digital verifiedidentification system recited in claim 1 wherein said at least oneverification data element includes a unique identification number. 19.The digital verified identification system recited in claim 18 whereinsaid unique identification number includes a social security number. 20.The digital verified identification system recited in claim 18 whereinsaid unique identification number includes a driver's license number.21. The digital verified identification system recited in claim 18wherein said unique identification number includes a credit card number.22. The digital verified identification system recited in claim 1wherein said at least one verification data element includes a usernameand a password.
 23. A digital verified identification system,comprising: a module generating assembly structured to receive at leastone verification data element corresponding to at least one entity andcreate at least one digital identification module, wherein said at leastone digital identification module is structured to be associated withsaid at least one entity, said at least one digital identificationmodule further structured to be embedded within at least one electronicfile, said at least one digital identification module comprising atleast one primary component structured to at least partially associatesaid at least one digital identification module with said at least oneentity, wherein said at least one primary component includes a digitalsignature, wherein said at least one digital identification module iscooperatively structured to be embedded within only a single electronicfile.
 24. The digital verified identification system recited in claim 23further comprising a plurality of corresponding metadata components. 25.The digital verified identification system recited in claim 23 whereinsaid at least one electronic file is pre-selected.
 26. A method ofdigital identification verification, comprising: receiving at least oneverification data element from an entity, creating at least one digitalidentification module corresponding to the entity, wherein the digitalidentification module includes at least one primary component at leastpartially associated with the entity, and embedding the at least onedigital identification module within an electronic file, wherein said atleast one digital identification module is cooperatively structured tobe embedded within only a single electronic file.
 27. The method asrecited in claim 26 further comprising defining receiving at least oneverification data element from the entity as receiving a valid usernameand password from the entity.
 28. The method as recited in claim 26further comprising defining receiving at least one verification dataelement from the entity as receiving at least one unique identificationnumber from the entity.
 29. The method as recited in claim 26 furthercomprising verifying the at least one verification data element.
 30. Themethod as recited in claim 26 further comprising combining at least oneprimary component with at least one metadata component to at leastpartially create the at least one digital identification module.
 31. Themethod as recited in claim 30 further comprising activating the digitalidentification module in response to at least one predetermined event.32. The method as recited in claim 31 further comprising defining the atleast one predetermined event as hovering a pointing device over theprimary component.
 33. The method as recited in claim 31 furthercomprising defining the at least one predetermined event as clicking onthe primary component with a pointing device.
 34. The method as recitedin claim 31 further comprising revealing the at least one metadatacomponent in response to activating the digital identification module.35. The method as recited in claim 30 further comprising communicatingat least one reference code to a third party.
 36. The method as recitedin claim 35 further comprising revealing the at least one metadatacomponent in response to communicating at least one reference code to athird party.
 37. The method as recited in claim 32 further comprisingpre-selecting the electronic file.
 38. The method as recited in claim 32further comprising pre-selecting a number of electronic files.
 39. Amethod of verifying the identification of an entity associated with anelectronic file, comprising: receiving at least one verification dataelement from the entity, creating at least one digital identificationmodule corresponding to the entity by at least partially combining aprimary component with at least one metadata component, wherein theprimary component includes a digital signature, and embedding the atleast one digital identification module within the electronic file,wherein said at least one digital identification module is cooperativelystructured to be embedded within only a single electronic file.